-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
test: removes e2e tests in favor of the sdk-tests suite #155
Conversation
736b3c8
to
0cd1a00
Compare
8050f95
to
86fc0b2
Compare
182d15f
to
ab67390
Compare
Will we no longer run these tests on the PR? I know they are now in the test suite, when does the test suite run? Do we plan to have anything in place to prevent merging PRs that are breaking the tests in the test suite? |
currently that test suite is run manually, but we are working on getting it in CI so eventually they should run on SDK PRs |
e2cdc67
to
e3fd888
Compare
Got it, how do you feel about waiting to merge this PR until the CI is updated? I fear removing these could slow development and make it harder to test. |
720ac40
to
7988bec
Compare
none of the sdks will get published until they pass the sdk tests anyways, so these tests don't have too much bearing on the release readiness. but it doesn't hurt to keep them in either so not opposed to keeping them until the CI is hooked up. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sounds good. My reason to suggest the waiting to merge is to make it easier during development. If a test fails we won't have to open an additional PR to fix anything we might miss.
e3fd888
to
2cf78c8
Compare
2cf78c8
to
f676461
Compare
Quality Gate passedIssues Measures |
BEGIN_COMMIT_OVERRIDE
feat!: return void instead of boolean for
Passage.user.delete
END_COMMIT_OVERRIDE
What's New?
Screenshots (if appropriate):
Type of change
Checklist:
Additional context